2 types accepted:
- <package>
- <chart>/<version>/<package>

- InitDependencies handle the version rules and the lifecycle rules that will be needed to calculate the next version
- GetPackages is used for "make prepare, patch and charts"

Adding new fields:
- Auto (bool type) will come from the new package.yaml
- AutoGeneratedBumpVersion that will be calculated at the end of the process

Also Fixed GetGithubRepository branch variable which was not being used

This method will enforce that the package.yaml for an auto-chart-bump is following the standards.
The standards will be defined at the rancher/charts/wiki.
They were already discussed with the chart owner (rancher-cis-operator).
They will serve as a standard for all other chart owners that desire to adopt the feature

Adding checks for the upstream chart options.
This means the variables that are used to check the upstream chart repository.
Where the update will come from.

Adding checks for the upstream additional charts that problably will be CRDs.
On this part of the code there will probably exist needed modifications for new chart owners.
That will need to be evaluated in the future.

…lete

Adding documentation
Adding re-use of the general methods that are already used in the release process.

This is the most important feature.

- The loading of versions must check/parse the latest version(from the index.yaml),
- The loading of versions must check/parse the upstream version to release,
- the rules for version bumps must be applied: (Only +1 minor/patch bump per PR).

Build the AutoGeneratedBumpVersion at the end of the process

The latest version comes from the actual index.yaml which was already sorted.
The assetsVersionsMap was loaded from lifecycle.InitDependencies

parse/separate the latest version that might come in one of the following formats:
- 10X.Y.Z+upa.b.c
- a.b.c

- get the version to release from the upstream repository
- check if it is coming with a repo prefix version (it should never come with it)
- check if the version to release is newer or the same as the latest version
  - if it is the same it is an rc bump and it is ok

small modification without breaking changes at generally used function for pulling upstream repository

rules:
- If chart version bump was patch -> repoPrefixVersion bumps patch
- If chart version bump was Minor Or Major -> repoPrefixVersion bumps minor

The only major bump on repoPrefixVersion is when we have minor version bump of Rancher:
- Rancher  v2.9 - 104
- Rancher v2.10 - 105

adding the update to the release.yaml file

…nerated in the previous commits

- adding support for autoGenBumpVersion
- not breaking any previous behavior

separating the version parsing and adding override for autoGenBumpVersion

- no changes here, just refactor

These fields were already present but not being used.

…stead of the legacy one